Silent store detection and recording in memory storage

ABSTRACT

An aspect includes receiving a write request that includes a memory address and write data. Stored data is read from a memory location at the memory address. Based on determining that the memory location was not previously modified, the stored data is compared to the write data. Based on the stored data matching the write data, the write request is completed without writing the write data to the memory and a corresponding silent store bit, in a silent store bitmap is set. Based on the stored data not matching the write data, the write data is written to the memory location, the silent store bit is reset and a corresponding modified bit is set. At least one of an application and an operating system is provided access to the silent store bitmap.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

This invention was made with Government support under B599858 awarded byDepartment of Energy. The Government has certain rights to thisinvention.

BACKGROUND

Various embodiments of this disclosure relate to memory storage, and,more particularly, to silent store detection and recording in memorystorage.

In many computer applications such as high performance computing andnumerical analysis, the same value is written to the same memorylocation several times. These repeated writes of the same values arereferred to as silent stores.

SUMMARY

Embodiments include methods, systems, and computer program products forsilent store detection and recording in memory storage. A methodincludes receiving a write request, the write request including a memoryaddress and write data. Stored data is read from a memory location atthe memory address. It is determined whether previous write requestsspecifying the memory address resulted in a write to the memorylocation. The determining is based on a value of a modified bit, in amodified bitmap, that corresponds to the memory address. The modifiedbit has a value of set when the memory location was previously writtento and a value of reset when the memory location was not previouslywritten to. Based on determining that the memory location was notpreviously written to, the stored data is compared to the write data.Based on the stored data matching the write data, the write request iscompleted without writing the write data to the memory and a silentstore bit, in a silent store bitmap, that corresponds to the memoryaddress is set to indicate that the write request was completed withoutwriting the write data to the memory. Based on the stored data notmatching the write data, the write data is written to the memorylocation, the silent store bit is reset to indicate that the writerequest was completed by writing the write data to the memory, and themodified bit is set to indicate that the write request was completed bywriting the write data to the memory location. Based on determining thatthe memory location was previously written to: the write data is writtento the memory location, the silent store bit is reset to indicate thatthe write request was completed by writing the write data to the memory,and the modified bit is set to indicate that the write request wascompleted by writing the write data to the memory location. At least oneof an application and an operating system is provided access to thesilent store bitmap.

Additional features and advantages are realized through the techniquesof the present invention. Other embodiments and aspects of the inventionare described in detail herein and are considered a part of the claimedinvention. For a better understanding of the invention with theadvantages and the features, refer to the description and to thedrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter which is regarded as the invention is particularlypointed out and distinctly claimed in the claims at the conclusion ofthe specification. The forgoing and other features, and advantages ofthe invention are apparent from the following detailed description takenin conjunction with the accompanying drawings in which:

FIG. 1 is a block diagram of a system for silent store detection andrecording in memory storage in accordance with an embodiment;

FIG. 2 is a block diagram of a memory and a silent store bitmap inaccordance with an embodiment;

FIG. 3 is a flow diagram of a process for silent store detection andrecording in memory storage in accordance with an embodiment;

FIG. 4 is block diagram of a state diagram of settings for a modifiedbit and a silent store bit in accordance with an embodiment;

FIG. 5 is a block diagram of a system for silent store detection andrecording in memory storage in accordance with an embodiment; and

FIG. 6 is a block diagram of a computing device for implementing some orall aspects of the system for silent store detection and recording inmemory storage in accordance with an embodiment.

DETAILED DESCRIPTION

Various embodiments of this disclosure relate to the detection andrecording of silent stores. By using a bitmap to track silent stores,embodiments provide for the tracking and recording of silent stores at alarge granularity when compared to contemporary solutions which arelimited to tracking silent stores across a fixed number of instructions(e.g., 10, 20). In addition, embodiments provide applications andoperating systems with access to the silent store bitmap, therebyallowing them to have visibility into current silent store activity.

Turning now to FIG. 1, a block diagram of a system 100 for silent storedetection and recording in memory storage is generally shown inaccordance with an embodiment. The system 100 includes a processor 102that executes an application and/or operating system (OS) that canrequest access to data stored in a memory 106. Requests of reads orwrites to the memory 106, from the processor 102, are sent to a memorycontroller 104 for processing. The memory controller 104 can perform anumber of tasks including, but not limited to, translation of virtualaddresses to real addresses, and buffering of requests. In embodimentsdescribed herein, the memory controller 104 can also perform silentstore detection and recording. Though shown as separate physicalcomponents in FIG. 1, one or more of the memory controller 104, thememory 106, the silent store bitmap 108, the modified bitmap 110, andthe processor 102 can also be co-located on a single physical component.

In an embodiment, the memory 106 is main memory that is internal to theprocessor and implemented by a dynamic random access memory (DRAM)device. In an embodiment, the silent store bitmap 106 is stored on aDRAM and/or static random access memory (SRAM) device. In embodiments,the silent store bitmap 106 is located in the memory 106.

As described previously, a silent store occurs when write data receivedas part of a memory write request is the same as the data already stored(the stored data) at the memory location. In embodiments describedherein, the memory controller 104 can interface with a silent storebitmap 108 to record portions of the memory 106 where a silent store hasoccurred, that is when a write request was completed without physicallywriting the write data to the memory. The memory controller 104 can alsointerface with a modified bitmap 110 to record portions of the memory106 where an non-silent store has occurred. As shown in FIG. 1, contentsof the silent store bitmap 108 can be provided to applications and/orOSs executing on the processor 102 via, for example, a memory mappedinput/output (I/O).

Embodiments can be utilized by synchronized checkpoints of a computersystem, such as a supercomputer system. As used herein, the term“checkpoint” refers to the copying of an application's states to abackup storage at a particular time. To facilitate fault tolerance, thecheckpoint can be read in case an error is detected, in order to recoveran application state to that particular time in preparation forre-execution. As used herein, the term “supercomputer” refers to acomputer system where the computation capacity is large, such that it ismore vulnerable to failures than conventional systems due to the sheernumber of its components. Supercomputers are also known as highperformance computing (HPC) systems. The silent store profile capturedin the silent store bitmap 108 can help a user determine which portionof the application data changes frequently. Using this information, theuser can schedule checkpoints selectively based on the adaptivefrequency of change for different data of the same application. As usedherein, the term “adaptive frequency of change” refers to how often thestored values of the application changes due to changes in applicationactivities. The checkpoint schedule can vary based on current (e.g.,real-time) information about which data is frequently being updated. Inother embodiments, the determining the frequently changing data andscheduling of checkpoints is automated (e.g., performed by a computer).

Embodiments can also be utilized during application tuning for acomputer application. Silent store profiling can help a user observe ifthe chosen time step and interval of the application is sufficient tocause changes in the results. The user can then tune the applicationbased on the profiling, for example, to use a larger time step orinterval for the simulations.

Embodiments can further be utilized by synchronous checkpoint restartsof a computer system. Silent store profiling can help a user determinehow often the application data changes in order to schedule checkpointsbased on the adaptive frequency of change for the application.Determining what portion of the application data to checkpoint can bebased on the silent store profile adaptively in real-time and/or basedon an off-line profile. After an optimal checkpoint schedule is chosen,at the checkpoint time the user can further benefit from the silentstore profile at runtime by copying only changed data.

Generally, techniques that benefit from tracking writes (e.g., using atranslation look-aside buffer (TLB) or other means) can further benefitfrom the silent store recording implemented by embodiments describedherein. Embodiments described herein can provide a more preciseindication (than, e.g., a TLB) of whether a change has occurred in adata region.

The checkpoint schedule can vary based on current (e.g., real-time)information about which data is frequently being updated. In otherembodiments, the determining the frequently changing data and thescheduling of checkpoints is automated (e.g., performed by a computer).

Turning now to FIG. 2, a block diagram 200 of a memory 202, a silentstore bitmap 204, and a modified bitmap 206 is generally shown inaccordance with an embodiment. In an embodiment, each section of thememory 202 corresponds to one bit in the silent store bitmap 204 and onebit in the modified bitmap 206. The size of the section can vary and canbe based on the number of bytes (or bits) that are read from the memory202 as a single unit and written to the memory 202 as a single unit. Inan embodiment where a DRAM line (the amount read or written as a unit)is 16 bytes, each section can contain 16 bytes of data to match the sizeof the DRAM line. In this embodiment, a destructive write of DRAMrequires the full 16-byte line to be read. Embodiments can implementsections of any size (e.g., 4 bytes, 8 bytes, 128 bytes, etc.), with thesize varying based on implementation requirements. In embodiments, eachsection is individually addressable via a memory address and alsoreferred to herein as a memory location. Thus, each memory addresscorresponds to a bit in the silent store bitmap 204 and to a bit in themodified bitmap 206. In embodiments the silent store bitmap 204 and themodified bitmap 206 can vary in size based on the size of the sectionsand the memory 202. In one embodiment, the silent store bitmap 204 andthe modified bitmap each contain 32 bytes.

Turning now to FIG. 3, a flow diagram 300 of a process for silent storedetection and recording in memory storage is generally shown inaccordance with an embodiment. In an embodiment, the process shown inFIG. 3 can be implemented by instructions located on a memory controllerand/or processor. At block 302, a write request that can include amemory address and write data is received. At block 304, the stored data(or read data), together with the corresponding modified bit and silentstore bit, is read from a memory location at the memory addressspecified by the write request. At 305, if it is determined that thememory block has already been modified, then the processing continues atblock 310, otherwise the processing continues to block 306. At block306, the stored data (or read data) is compared to the write dataspecified by the write request. If it is determined, at block 308 thatthe content matches, then a silent store has been detected andprocessing continues at blocks 314-316. If it is determined, at block308 that the content does not match, then a silent store has not beendetected and processing continues at blocks 310-313.

At block 310 of FIG. 3, based on the stored data not matching the writedata (i.e., the write does not cause a silent store), the write data iswritten to the memory location. In an embodiment, a corresponding bit inthe silent store bitmap can be reset, at block 312, to indicate that thewrite data was written. At block 313, the corresponding bit in themodified bitmap can be set.

In an embodiment, the write at block 310 is performed only when thestored data does not match the write data. In this embodiment, whenblock 310 is performed after block 305 results in a “yes” (e.g., themodified bit is set), the stored data is compared to the write dataprior to block 310 being performed and the writing at block 310 occursonly when the stored data does not match the write data. When the storeddata does not match the write data, the process flows from block 305 toblock 312.

At block 314 of FIG. 3, the write request is completed without writingthe write data to the memory location. The process can includedetermining whether any previous write requests resulted in a write tothe memory location and at block 316, and based on determining that theprevious write requests did not result in a write to the memorylocation, the silent store bit that corresponds to the memory address isset in the silent store bitmap to indicate that the write request wascompleted without writing the write data to the memory. In embodiments,the determining whether previous write requests specifying the memoryaddress resulted in a write to the memory location includes looking asfar back as a specified time frame, a specified number of total writesto the memory system, and/or since the last initialization of the silentstore bitmap. In embodiments, and as described below with reference toFIG. 4, a modify bit associated with the memory address can be used todetermine whether the memory location was previously updated.

In an embodiment, the bits in a silent store bitmap are reset when thesilent store bitmap is initialized. In addition, the bits in the silentstore bitmap can be reset after events that include, but are not limitedto: a checkpoint is completed, after an application has completedexecution, and/or after contents of the memory have been transmitted toanother processor. In an embodiment, during an initialization of thesilent store bitmap all of the bits are reset (e.g., to “0”). When asilent store occurs, the corresponding bit in the silent store bitmap isset (e.g., to “1”).

In an embodiment, the bits in a modified bitmap are reset when themodified bitmap is initialized. In addition, the bits in the modifiedbitmap can be reset after events that include, but are not limited to: acheckpoint is completed, after an application has completed execution,and/or after contents of the memory have been transmitted to anotherprocessor. In an embodiment, during an initialization of the modifiedbitmap all of the bits are reset (e.g., to “0”). When a non-silent storeoccurs (i.e., a physical write to the memory occurs), the correspondingbit in the modified bitmap is set (e.g., to “1”).

In embodiments, the silent store bitmap and the modified bit map areinitialized at the same time. Also, in embodiments, the bits in thesilent store bitmap and the modified bitmap are reset in response to thesame events.

In embodiment, the silent store bitmap and the modified bitmap are madeaccessible to an application and/or to an operating system. In anembodiment, access is provided via memory mapped I/O, such that the OSor user can access the silent store and modified bitmaps through memoryaccess instructions (e.g., load and store instructions) or a directmemory access (DMA) engine. A mapping data structure that establishes adata memory addresses to an address where the data memory'scorresponding silent store bit and modified bit are located ismaintained in the OS. In one embodiment, a mapping of a data virtualaddress page to its corresponding modified and silent store bitmap ismaintained in OS, and individual modified and silent store bits can belocated by using lower bits of the data virtual address as a bitposition offset to the corresponding bitmap. The access method throughmemory mapped I/O also enables an OS the ability to reset the silentstore and modified bitmaps, at the beginning of a checkpoint cycle ormemory initialization.

Turning now to FIG. 4, a block diagram of a state diagram 400 ofsettings for a modified bit and a silent store bit is generally shown inaccordance with an embodiment. In embodiment, a modify bit associatedwith the memory address can be used to determine whether the memorylocation was not previously updated. The modify bit can stored in thememory with the stored data, for example, as metadata, and included aspart of the read data from the memory location.

As shown in the state diagram 400 of FIG. 4, a modified bit initialstate 402, a silent store bit initial state (from the silent statebitmap), and an incoming store state 406 (i.e., silent store or not asilent store) are input to the state diagram 400. Output from the statediagram 400 are a new modified bit state 408 and a new silent store bit410. For example, if the modified bit initial state 402 is “0” (thememory address has not been previously modified), the silent store bitinitial state 404 is “0” (the last store was not a silent store), andthe incoming store state 406 is a silent store, then the result is thatthe new modified bit state 408 is “0” and the new silent store bit 410is set to “1” to indicate that a silent store has occurred. As shown inthe state diagram, the only time that the silent store bit can have avalue of “1” is when the modified bit initial state 402 is “0” (thememory location was not previously modified) and the incoming storestate 406 is a silent store.

Turning now to FIG. 5, a block diagram of a system 500 for silent storedetection and recording in memory storage is generally shown inaccordance with an embodiment. The system 500 includes an accelerator504 that executes an application and/or operating system (OS) that canrequest access to data stored in a memory 510. Requests of reads orwrites to the memory 510, from the accelerator 504, are sent to a memorycontroller 508 for processing. The memory controller 508 can perform anumber of tasks including, but not limited to, translation of virtualaddresses to real addresses, and buffering of requests. In embodimentsdescribed herein, the memory controller 508 can also perform silentstore detection and recording using the silent store bitmap 506 and themodified bitmap 512.

In an embodiment, the memory 510 is main memory that is internal to theaccelerator 504 and implemented by a dynamic random access memory (DRAM)device. In an embodiment, the silent store bitmap 506 and/or modifiedbitmap 512 is stored on a DRAM and/or static random access memory (SRAM)device. In embodiments, the silent store bitmap 506 and/or the modifiedbitmap 512 is located in the memory 510.

In an embodiment, such as that shown in FIG. 5, that includes aheterogeneous system that includes a processor 502 (e.g., a generalpurpose processor or host processor) and an accelerator 504 such as agraphics processing unit (GPU), the accelerator 504 can send computerinformation (e.g., data) back to the CPU 502 at the end of computationin certain time steps. With silent store record according to embodimentsdescribed herein, the accelerator 504 can send only data that aredifferent from the data that the CPU 502 already received in the lasttime step. For a user application, sending data back infrequently canresult in a stall latency, while sending data back too frequentlyresults in inefficiency (more transfers of the same data). By usingembodiments of the silent store profiling described herein, a user (orcomputer if automated) can determine an optimal, adaptive time step toschedule sending back of data.

Turning now to FIG. 6, a block diagram of a computer system 600 for usein implementing some of all aspects of the system for silent storedetection and recording in memory storage is generally shown accordingto some embodiments. The processing described herein may be implementedin hardware, software (e.g., firmware), or a combination thereof. In anexemplary embodiment, the methods described may be implemented, at leastin part, in hardware and may be part of the microprocessor of a specialor general-purpose computer system 600, such as a personal computer,workstation, minicomputer, or mainframe computer.

In an exemplary embodiment, as shown in FIG. 6, the computer system 600includes a processor 605, memory 610 coupled to a memory controller 615,and one or more input devices 645 and/or output devices 640, such asperipherals, that are communicatively coupled via a local I/O controller635. These devices 640 and 645 may include, for example, a printer, ascanner, a microphone, and the like. A conventional keyboard 650 andmouse 655 may be coupled to the I/O controller 635. The I/O controller635 may be, for example, one or more buses or other wired or wirelessconnections, as are known in the art. The I/O controller 635 may haveadditional elements, which are omitted for simplicity, such ascontrollers, buffers (caches), drivers, repeaters, and receivers, toenable communications.

The I/O devices 640, 645 may further include devices that communicateboth inputs and outputs, for instance disk and tape storage, a networkinterface card (NIC) or modulator/demodulator (for accessing otherfiles, devices, systems, or a network), a radio frequency (RF) or othertransceiver, a telephonic interface, a bridge, a router, and the like.

The processor 605 is a hardware device for executing hardwareinstructions or software, particularly those stored in memory 610. Theprocessor 605 may be a custom made or commercially available processor,a central processing unit (CPU), an auxiliary processor among severalprocessors associated with the computer system 600, a semiconductorbased microprocessor (in the form of a microchip or chip set), amacroprocessor, or other device for executing instructions. Theprocessor 605 includes a cache 670, which may include, but is notlimited to, an instruction cache to speed up executable instructionfetch, a data cache to speed up data fetch and store, and a translationlookaside buffer (TLB) used to speed up virtual-to-physical addresstranslation for both executable instructions and data. The cache 670 maybe organized as a hierarchy of more cache levels (L1, L2, etc.).

The memory 610 may include one or combinations of volatile memoryelements (e.g., random access memory, RAM, such as DRAM, SRAM, SDRAM,etc.) and nonvolatile memory elements (e.g., ROM, erasable programmableread only memory (EPROM), electronically erasable programmable read onlymemory (EEPROM), programmable read only memory (PROM), tape, compactdisc read only memory (CD-ROM), disk, diskette, cartridge, cassette orthe like, etc.). Moreover, the memory 610 may incorporate electronic,magnetic, optical, or other types of storage media. Note that the memory610 may have a distributed architecture, where various components aresituated remote from one another but may be accessed by the processor605.

The instructions in memory 610 may include one or more separateprograms, each of which comprises an ordered listing of executableinstructions for implementing logical functions. In the example of FIG.6, the instructions in the memory 610 include a suitable operatingsystem (OS) 611. The operating system 611 essentially may control theexecution of other computer programs and provides scheduling,input-output control, file and data management, memory management, andcommunication control and related services.

Additional data, including, for example, instructions for the processor605 or other retrievable information, may be stored in storage 620,which may be a storage device such as a hard disk drive or solid statedrive. The stored instructions in memory 610 or in storage 620 mayinclude those enabling the processor to execute one or more aspects ofthe dispatch systems and methods of this disclosure.

The computer system 600 may further include a display controller 625coupled to a display 630. In an exemplary embodiment, the computersystem 600 may further include a network interface 660 for coupling to anetwork 665. The network 665 may be an IP-based network forcommunication between the computer system 600 and an external server,client and the like via a broadband connection. The network 665transmits and receives data between the computer system 600 and externalsystems. In an exemplary embodiment, the network 665 may be a managed IPnetwork administered by a service provider. The network 665 may beimplemented in a wireless fashion, e.g., using wireless protocols andtechnologies, such as WiFi, WiMax, etc. The network 665 may also be apacket-switched network such as a local area network, wide area network,metropolitan area network, the Internet, or other similar type ofnetwork environment. The network 665 may be a fixed wireless network, awireless local area network (LAN), a wireless wide area network (WAN) apersonal area network (PAN), a virtual private network (VPN), intranetor other suitable network system and may include equipment for receivingand transmitting signals.

Systems and methods to perform to silent store detection and recordingin memory storage according to this disclosure may be embodied, in wholeor in part, in computer program products or in computer systems 600,such as that illustrated in FIG. 6.

Technical effects and benefits of embodiments include the ability totrack and record silent stores at a large granularity when compared tocontemporary solutions. In addition, embodiments provide applicationsand operating systems with visibility into current silent storeactivity.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiments were chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Java, Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A method for detecting and recording silentstores in a memory system, the method comprising: receiving a writerequest, the write request including a memory address and write data;reading stored data from a memory location at the memory address;determining whether previous write requests specifying the memoryaddress resulted in a write to the memory location, the determiningbased on a value of a modified bit, in a modified bitmap, thatcorresponds to the memory address, the modified bit having a value ofset when the memory location was previously written to and a value ofreset when the memory location was not previously written to; based ondetermining that the memory location was not previously written to:comparing the stored data to the write data; based on the stored datamatching the write data, completing the write request without writingthe write data to the memory and setting a silent store bit, in a silentstore bitmap, that corresponds to the memory address to indicate thatthe write request was completed without writing the write data to thememory; based on the stored data not matching the write data, writingthe write data to the memory location, resetting the silent store bit toindicate that the write request was completed by writing the write datato the memory, and setting the modified bit to indicate that the writerequest was completed by writing the write data to the memory location;based on determining that the memory location was previously written to:writing the write data to the memory location, resetting the silentstore bit to indicate that the write request was completed by writingthe write data to the memory, and setting the modified bit to indicatethat the write request was completed by writing the write data to thememory location; comparing the stored data to the write data based ondetermining that the modified bit is set, wherein the writing the writedata to the memory location, resetting the silent store bit to indicatethat the write request was completed by writing the write data to thememory, and setting the modified bit to indicate that the write requestwas completed by writing the write data to the memory location based ondetermining that the memory location was previously written to isfurther based on the stored data not matching the stored data; providingat least one of an application and an operating system access to thesilent store bitmap; performing a checkpoint, the performing includingusing the silent store bitmap to determine which memory locations in thememory system to copy as part of the checkpoint; and scheduling thecheckpoint based on contents of the silent store bitmap; wherein silentstore bits in the silent store bitmap are reset when the silent storebitmap is initialized and modified bits in the modified bitmap are resetwhen the modified bitmap is initialized; wherein content of the silentstore bitmap is accessed by the at least one of the application and theoperating system via a memory mapped input/output interface; wherein thememory system is included in an accelerator device and contents of thesilent store bitmap are used to determine when to send data from atleast a portion of the memory locations from the accelerator device to ageneral purpose device; wherein the determining whether previous writerequests specifying the memory address resulted in a write to the memorylocation includes at least one of previous write requests within aspecified time frame, previous write requests within a specified numberof total writes to the memory system, and previous write requests sincea last initialization of the silent store bitmap.